Method And Apparatus For Sharing TCAP Traffic Load

ABSTRACT

The present invention relates to a point code emulation apparatus and method for dividing a Common Channel Signaling System No. 7 (or SS7) signaling network into two or more networks. The point code emulator is adapted to receive TCAP messages from two or more subnets and converts, for the messages crossing over the subnets, the information of the TCAP messages, including originating point code, destination point code, and transaction identifier, (and optionally, calling party number and called party number), and forwards to the other one of the two or more subnets. Correspondence among the two or more subnets may be provisioned by an authorized user of the system, may be learned automatically by the system based on ISUP message correspondences or previous TCAP transactions, or may be automatically discovered by the system broadcasting messages to nodes in the destined one of the two or more subnets.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of application Ser. No. 13/874,302,filed on Apr. 30, 2013, which is a continuation of application Ser. No.12/528,652 filed Aug. 26, 2009, now U.S. Pat. No. 8,452,890, which wasthe National Stage of International Application No. PCT/US2007/087636filed Dec. 14, 2007, which claims the benefit of U.S. ProvisionalApplication No. 60/891,692 filed Feb. 26, 2007.

FIELD OF THE INVENTION

The present invention relates to a point code emulation apparatus,system and method for dividing a Common Channel Signaling System No. 7(or SS7) signaling network into two or more networks.

BACKGROUND OF THE INVENTION

Common Channel Signaling System No. 7 (or SS7) is a global standard fortelecommunications defined by the International Telecommunication UnionTelecommunication Standardization Sector (or ITU-T). The standarddefines the procedures and protocol by which network elements in thepublic switched telephone network (PSTN) exchange information over adigital signaling network to effect wireless (cellular) and wirelinecall setup, routing and control. The ITU definition of SS7 allows fornational variants such as the American National Standards Institute(ANSI) and Bell Communications Research (Telcordia Technologies)standards used in North America, the European TelecommunicationStandards Institute (ETSI) standard used in Europe, and theTelecommunication Technology Committee (TTC) standard used in Japan. SS7messages are exchanged between network elements over 56 or 64 kilobitper second (kbps) bi-directional channels called signaling links, or canbe exchanged over the Internet Protocol or over ATM in a point-to-pointor networking fashion using adaptation layers. As SS7 network evolves,more transparent methods and protocols can be defined.

Each signaling point in the SS7 network is uniquely identified by anumeric point code. Point codes are carried in signaling messagesexchanged between signaling points to identify the source anddestination of each message. However, as the network grows its size andcomplexity, new point codes would eventually become scarce and, thuscreating such new point codes would be very expensive. Re-architecturinga signaling network, i.e. adding a new network (or network elements) ordeleting a part of the network could also be time consuming and oftenrequires reprogramming the switches according to the new networkarchitecture, thus it is desirable to have a method and apparatus forexpanding the network without going through such networkrearchitecturing.

There are a couple of prior art systems attempted to solve such issues.For example, U.S. Pat. No. 6,987,781, entitled “Methods and Systems forRouting signaling Messages in a Communication Network Using CircuitIdentification Code (CIC) Information”, issued to Miller et al on Jun.17, 2006 relates to a routing node for receiving, processing andsubsequently transmitting SS7 signaling messages destined for a MediaGateway Controller type network element, where the network element is aCIC routing node adapted to receive ISUP messages from an associated SS7network and determine the routing destination of the messages based onoriginating point code (or OPC), destination point code (or DPC) andcircuit identification code (or CIC). However, in this prior system,such conversion is limited to ISUP messages, thus it would not be ableto extend the services using other message types, such as SCCP or TCAPmessages, thus this is a limitation of this solution.

SUMMARY OF THE INVENTION

The present invention relates to a point code emulation apparatus,system and method for dividing a Common Channel Signaling System No. 7(or SS7) signaling network into two or more networks.

One object of the present invention is to overcome the limitation on thenumber of addressable nodes in a network, and, to provide a method andapparatus for expanding and extending the network without having tore-architecting the entire SS7 signaling network.

Another object of the present invention is to divide the SS7 signalingnetwork into two or more subnets.

Yet another object of the present invention is to provide a system forsharing TCAP traffic load among a plurality of nodes in a subnet byhiding details of the subnet.

According to one aspect of the invention, it provides a method ofrouting a TCAP message for dividing a SS7 signaling network into two ormore subnets, comprising the steps of: (i) receiving the TCAP messagefrom one of the two or more subnets; (ii) extracting OPC, DPC and TID ofthe TCAP message; (iii) looking up and retrieving, from a plurality ofstructured data storages, a corresponding OPC, a corresponding DPC and acorresponding TID for the other one of the two or more subnets based,partially or combinedly, on the OPC, the DPC and the TID of the receivedTCAP message; (iv) replacing the OPC, the DPC, and/or the TID of thereceived TCAP message with the corresponding OPC, the corresponding DPCand/or the corresponding TID; and (v) forwarding the TCAP message withthe corresponding OPC, the corresponding DPC and the corresponding TIDto the other one of the two or more subnets.

According to another aspect of the invention, it provides a computerreadable medium storing executable computer program instructions which,when executed at a node, cause the node to perform a process of routinga TCAP message between two or more subnets of a SS7 signaling network,comprising steps of: (i) receiving said TCAP message from one of the twoor more subnets; (ii) extracting OPC, DPC and TID of the TCAP message;(iii) looking up and retrieving, from a plurality of structured datastorages, a corresponding OPC, a corresponding DPC and a correspondingTID for the other one of the two or more subnets based, partially orcombinedly, on the OPC, the DPC and the TID of the received TCAPmessage; (iv) replacing the OPC, the DPC, and/or the TID of the receivedTCAP message with the corresponding OPC, the corresponding DPC and/orthe corresponding TID; and (v) forwarding the TCAP message with thecorresponding OPC, the corresponding DPC and the corresponding TID tothe other one of the two or more subnets.

According to yet another aspect of the invention, it provides a networkapparatus for routing a TCAP message between at least two subnets of aSS7 signaling network, comprising: (i) a corresponding number ofinterfaces to said at least two subnets of said SS7 signaling networkfor interfacing with said at least two subnets; (ii) a plurality ofstructured data storages; and (iii) a processor in communication withthe corresponding number of the interfaces and the plurality of datastorage, wherein the processor is for carrying out a process of saidrouting said TCAP message between said at least two subnets, saidprocess comprising the process of:—receiving said TCAP message from oneof the two or more subnets;—extracting OPC, DPC and TID of the TCAPmessage;—looking up and retrieving, from the plurality of structureddata storages, a corresponding OPC, a corresponding DPC and acorresponding TID for the other one of said two or more subnets based,partially or combinedly, on the OPC, the DPC and the TID of the receivedTCAP message; replacing the OPC, the DPC, and/or the TID of the receivedTCAP message with the corresponding OPC, the corresponding DPC and/orthe corresponding TID; and—forwarding the TCAP message with thecorresponding OPC, the corresponding DPC and the corresponding TID tothe other one of the two or more subnets.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will now be described in more detail with reference to theaccompanying drawings, in which:

FIG. 1 is an overview of a point code emulation of a preferredembodiment of the present invention;

FIG. 2 is a simplified network diagram showing TCAP message flow from anode in Private Network;

FIG. 3 is a simplified network diagram showing TCAP message flow from anode in Public Network;

FIG. 4 is a call flow diagram showing a case for TCAP broadcasting;

FIG. 5 is a call flow diagram showing a case for TCAP learning fromprevious TCAP message;

FIG. 6 is a call flow diagram showing a case for ISUP learning;

FIG. 7 is a process flow chart for handling a TCAP message originatedfrom a node in Public Network; and

FIG. 8 is a process flow chart for handling a TCAP message originatedfrom a node in Private Network.

DETAILED DESCRIPTION OF THE INVENTION

Referring to FIG. 1, a system 1 is a signal transfer point (STP) in aSS7 signalling network. The system 1 comprises a point code emulator 100interacting with SCCP 112 and MTP 113 in Public Network 10 side and withSCCP 122 and MTP 123 in Subnet (or Private Network) 20 side. The system1 further comprises GTT 111 at Public Network 10 side and GTT 121 atPrivate Network 20 side. The system 1 may interface with more than twonetwork segments or subnets. For each subnet, the system 1 would furthercomprises corresponding SCCP (not shown) and MTP (not shown), andcorresponding GTT (not shown), in communication with PCE 100.

The system 1 further comprises at least one structured data storagemeans 30, such as database, embedded within, externally accessible fromPCE 100, or internally accessible within the system 1 for recording,managing and querying point codes and trunk mappings for each subnet thesystem 1 is connected to, the data including, but not limited to, PublicNodes (or Nodes in Public Network 10), Private Nodes (or Nodes inPrivate Network 20), Public gateway, GTT tunnel Gateways, trunk mappingsand ISUP Learning Exceptions.

The Public Nodes define the switches in Public Network 10 while thePrivate Nodes define the switches in Private Network 20. The PublicGateway represents the point code presence in Public Network 10 toaccess Private Network 20. The GTT Tunnel Gateway represents the GTTTunnel point codes in both Public Network 10 and Private Network 20 forthe TCAP management bypass. The Trunk Mapping is used for ISUP trafficonly by defining CIC range maps.

A Public Node record is created for every switch in Public Network 10,which requires access to Private Network 20. The Public Node records arestored/managed in the database. It is noted that the Public Nodes arenot limited to switches/nodes adjacent to the system 1 in Public Network10. For TCAP traffic, the number of Public Nodes can be in the hundredsdue to Private Network 20 initiated transaction with Point Code-SubSystem Number (or PC-SSN) routing. It is preferable that two hash tablesmay be utilized for efficient querying, i.e. one for the messages viaPublic Home Point Code and the other with Point Code for Private Network20.

A Private Node record is created for every switch in Private Network 20.For TCAP only traffic, Private Node records may not be required due toGTT Routing and Transaction Id (or TID) records which keep track of theoriginating Point Code of the switch/node in Private Network 20.

PCE 100 typically supports a single Point Code presence in PublicNetwork 10 via a Public Gateway record for interacting with nodes inPrivate network 20. A second Public Gateway record can be created ifthere are multiple Point Code presences available in Public Network 10.Multiple Public Gateway deployment is used when two existing correlatedswitches are extracted from a network to form the expanding Privatenetwork 20. The resulting Public Network 10 is already configured forthe two Point Code presences.

MTP 113 and MTP 123 handle inter-network traffic and intercept crossnetwork traffic. Virtual Nodes are defined in the MTP 123 forcorresponding a point code in Private Network 20 to relevant nodes inPublic Network 10. Virtual Nodes are also defined in MTP 113 forcorresponding Gateway Point Codes in Public Network 10 and for anycorresponding GTT tunnel Gateway Point Code(s).

SCCP 112 routes all TCAP traffic to PCE 100, which is same for PrivateNetwork 20, SCCP 122 routes all TCAP traffic to PCE 100 for GTT 111 andPoint Code-SubSystem Number (PC-SSN) routed traffic. SCCP Managementmessages (SCMG) are preferably processed locally within the associatednetwork side in which the messages are originated from, and thus are notcrossing over to the other side of the network.

The GTT 111 is used to route the TCAP transactions initiated by PublicNetwork 10 to Private Network 20 and the TCAP messages destined for PCEGTT Tunnelling (not shown).

The GTT Tunnelling is to bypass the TCAP transaction conversion forcertain SCCP services. For example, GSM traffic and LNP ANSI queriesmight originate from Private Network 20. As the GSM traffic is routed onGTT information but LNP is PC-SSN routed, the LNP queries would requireTCAP transaction management while the GSM message would be sent to theGTT directly via GTT Tunnelling.

The GTT Tunnelling can be identified by the incoming message'sDestination Point Code (DPC). Cross network configuration between thePrivate and Public tunnelling messages is required for proper routing atPCE 100 to the appropriate SCCP.

For GTT routing of Public initiated queries, the GTT Destination List isset to the necessary Private Network Appearance with its relevant pointcodes. This allows cross network transfer at the GTT 111. PCE 100 willforward the resulting message directly to SCCP 122 in Private Network 20side.

In the other embodiment of the present invention, the system 1 furtherpermits multiple Private Network Appearances to configure two switchesin Private Network 20 with the same point code.

TCAP transaction identifiers are up to 4 octets in length and are uniquefrom an origination switch to a given destination. Thus the combinationof OPC, DPC, and TID make a unique key.

As Nodes in Private Network 20 are usually not a one-to-one mapping tothe Public Gateways, each of the TIDs in TCAP messages originated fromPrivate Network 20 must be mapped to a unique value to ensure theiruniqueness in Public Network 10. For Public Nodes, the TID mapping isalso useful to keep track of the Public Gateway used to receive thepublic query such that the response uses the proper OPC back to PublicNetwork 10. It is noted that, in the case of a mated-pair configurationfor redundant SS7 traffic support, each PCE 100 must not duplicate theTIDs used to maintain their uniqueness.

The TID information may be stored and managed in a structured datastorage means, i.e. hash tables, to allow for efficient queries based onTIDs of the incoming TCAP messages. Preferably, PCE 100 comprises atleast two hash tables, one based on incoming original TID 41 and theother based on received TID 42. The original TID search is used duringconversation to find an existing record. The received TID is used tocorrelate bi-directional messages between TID records for Public Network10 and TID records for Private Network 20 during transaction completionfrom one of Public Network 10 and Private Network 20, whichever did notinitiate the original TCAP query. The received TID search is used duringresponses to find the original information.

When PCE 100 records the TIDs, each of the records is given an expirytime and a lifespan for the record, and such lifespan information may bemanaged using another structured data storage means, i.e. a list (or alifespan list) 43 and managed using timer related software object. Aslifespan value is individually assigned and managed for each of therecords and can be cleared in a first-in first-out fashion. PCE 100maintains the lifespan list 43 and, at every specific time interval, thefirst item (or the oldest item) in the lifespan list 43 is evaluated todetermine whether the lifespan is expired. Upon expiry of the lifespanof the oldest item, the lifespan list 43 is parsed from the head (oroldest one) toward the tail (or the youngest one). Each lifespan, whichis considered to be expired, is recycled and causes corresponding TIDrecords in the incoming original TID hash table 41 and/or the receivedTID hash table 42 to be recycled as well, and the timer is restarted ifnecessary.

FIG. 2 illustrates a typical TCAP message flow originating from aPrivate Node 231 to a Public Node 131 though PCE STP Mate 1 100M1 of thesystem 1M, which is in a mated-pair configuration with the system 1M′. ATCAP-Begin message is originated from Private Node 231 (PC value is1.1.1), bearing OPC value of 1.1.1, DPC value of 3.3.3 and TID value of000001 in the direction 51. PCE 100 intercepts the TCAP-Begin messageand stores TID and OPC in the hash table. PCE 100, then, replaces OPCvalue with 5.5.5, which is the PC of the system 1 for Public Network 10,and replaces TID value with an available unique TID value, i.e. 100001,in this example. PCE 100 forwards the message to Public Node 131. OncePublic Node 131 receives the message, then Public Node 131 generates aTCAP-Response message, bearing OPC value of 3.3.3, DPC value of 5.5.5,and TID value of 100001, and forwards the message in the direction 52.PCE 100 intercepts the TCAP-Response message and look up DPC and TID inthe hash table, and finds that Private Node 231 and TID value of 000001corresponds, thus replaces DPC and TID, accordingly. Then, PCE 100forwards the message to the Private Node 231.

FIG. 3 illustrates a typical TCAP message flow originating from a PublicNode having point code value 3.3.3 131 to a Private Node having pointcode value 1.1.1 231 through PCE STP Mate 1 100M1. For such case, theoperator of Private Network 20 provisions PCE 100 to either route allTCAP traffic designated to specific Public Gateway to a single node inPrivate Network 20, or retrieve a final destination from GTT 111 and/orGTT 121.

The Point Codes that are used to represent nodes in Private Network 20to Public Network 10 are known as Public Gateway Point Codes. Theoperator of Private Network 20 may choose to declare one privatedestination for a particular Public gateway point code. This would beappropriate if there is a Public Gateway Point Code(s) that are torepresent one application node in Private Network 20. This may be anuncommon usage of PCE 100, as one public destination is required to befixed to one private destination.

A TCAP Begin message is sent from Public Node 3.3.3 131 to PCE STPMate-1 100M1 in the direction 61, where the message bearing OPC value of3.3.3, DPC value of 5.5.5 (which is the system 1's PC value in PublicNetwork 10), and TID value of 000001. Assuming that the operator ofPrivate Network 20 or the authorized user of PCE 100 has beenprovisioned PCE 100 such that all TCAP Begin message sent to the system1 or Public Gateway Node at 5.5.5 should be directed to the private node1.1.1. In a case where the operator of Private Network 20 may haverather provisioned GTT 111 or/and 121 databases, thus for TCAPtransactions that originate (with a TCAP Begin message) from PublicNetwork 10, PCE 100 may interact with GTT to seek for a finaldestination in Private Network 20.

PCE 100 replaces the DPC value to 1.1.1 as provisioned and assign newvalue for TID, i.e. 100001, record TIDs in the TID hash tables, andforward the converted message to Private Node 1.1.1 231 in PrivateNetwork 20. Once Private Node 1.1.1 231 receives the TCAP Begin message,it generates the TCAP Response message bearing OPC value of 1.1.1, DPCvalue of 3.3.3, and TID value of 100001, and forwards the message in thedirection 62. PCE 100, again, intercepts the message and look upcorresponding TID for Public Network 10 from the hash tables 41 and 42,and retrieves the corresponding TID value, which is 000001. PCE 100converts OPC value to 5.5.5 and TID values to 000001, and forwards theconverted message to Public Node 3.3.3 131.

Occasionally, when the operator of Private Network 20 provisioned PCE100 to inquire GTT for resolving final destination for TCAP messagesoriginated from a node in Public Network 10, the result of the inquiryto GTT 121 and/or GTT 111 may be inconclusive. If the GTT information isinconclusive and traffic cannot be mapped one-to-one between the system1 (or the Public Gateway) and a node in Private Network 20, PCE 100 maybroadcast the message to all or designated nodes in Private Network 20.Once PCE 100 broadcasts the TCAP query to all or designated nodes inPrivate Network 20, PCE 100 waits for a successful response beforeforwarding the response back to the Public Node 131. PCE may,optionally, send the TCAP query to a randomly selected node(s) inPrivate Network 20. Upon reception of successful responses from thenodes in Private Network 20, the most successful one will be regarded asthe designation in Private Network 20 for the transaction.

If a broadcast has returned a successful response to one TCAP message,then it stands to reason that there is a TCAP request to the same calledparty afterwards. This would avoid broadcasting repeatedly to theswitches including the switch that just provided a positive response.Similarly, if a message comes from Private Network 20 with calling partyinformation, this information can be used to further learn aboutdestinations in Private Network 20.

FIG. 4 is a call flow chart illustrating TCAP broadcast learning method.Public Node 131 generates and transmits TCAP begin message 151 to PCE100. The PCE 100, then, broadcasts the messages 152 and 153 to allPrivate Nodes 231 and 232, respectfully, since PCE 100 could notdetermine to which node in Private Network 20 the message should berouted. Private Node 231 rejects, generates and transmits TCAP Rejectmessage 154 back to PCE 100. Private Node 232 accepts, generates andtransmits TCAP Response 155 to PCE 100. PCE 100 learns from thistransaction that the private node (or called party) that was able tosuccessfully terminate the TCAP Begin message from Public Node 131 wasPrivate Node 232. Subsequently, when PCE 100 receives another TCAP Beginmessage 157 from the same called party number, PCE 100 simply forwardsthe message 158 to Private Node 232.

FIG. 5 is a call flow chart illustrating learning method from TCAPmessage initiated from Private Network 20. Private Node 232 sends a TCAPBegin message 161 to PCE 100. PCE 100 converts and forwards TCAP Beginmessage 162 to Public Node 131, and make records of calling party digitsand TID information in the hash tables 41 and 42. Once Public Node 131receives TCAP Begin message 162, Public Node 131 generates and transmitsTCAP End message 163 to PCE 100. PCE 100 looks up and retrieve TID fromthe hash table 41 and 42, converts and transmits the message 164 toPrivate Node 232. Subsequently, Public Node 131 transmits a TCAP Beginmessage 165 to PCE 100. Based on the called party digits and theoriginator information, PCE 100 looks up and retrieve corresponding DPCand TID value from the hash tables 41 and 42. PCE 100, then, convertsand forwards the message 166 to Private Node 232.

ISUP traffic between the Public and a Private network is well defined bythe Trunk Mappings. For TCAP traffic, the TID mapping is unique forPrivate queries to Public Network 10 but not in the reverse direction.Typically, the GTT is configured to select the proper Private Node or abroadcast scheme can be used as described above. ISUP learning may beenabled or disabled by an authorized user.

For “class 5” functionality such as “*69” using TCAP queries, thepreceding ISUP IAM contains the digits information used in the TCAP SCCPCalled Party Address parameter. As the IAM already knows its destinationbased on its CIC, the Private Node can be learned for a given phonenumber.

The ISUP learned information should not be kept statically as phonenumbers can be ported and cell phones can roam. The ISUP learning digitshave a configurable lifespan set, preferably, in seconds. In thepreferred embodiment of the present invention, the lifespan is 1 day(86400 seconds).

ISUP learning is based on the IAM digits parameter(s) of interest. Forlocal number portability and other services which might affect thedialled digits, the ISUP Learning can be configured to process IAMCalled Party Number and/or Original Called Number for Public initiatedtraffic and/or IAM Calling Party Number for Private initiated traffic.

The ISUP Learning information has two types of distribution: broadcast,and query-and-response. For each types of distribution, the user may setthe ISUP Learning Max Delay parameter. In the preferred embodiment ofthe present invention, ISUP Learning Max Delay parameter may be set to 0for broadcast, and to a millisecond interval (1000 recommended) forPublic TCAP query ISUP Learning query to all peers with pendingresponse. The ISUP learning is digit based and is stored in a structureddata storage means 45, i.e. a number tree for quick access.

On receipt of learning digits, the number tree 45 is queried to see ifthe corresponding private node is already there in the record. If theISUP Learning record is not found, a new record is created. If therecord is found, the private node name is updated if necessary and thelifespan is reset.

Optionally, in order to maintain the number tree compact, if the ISUPLearning records count exceeds a certain number, i.e. 100,000, PCE 100forces the expiry of the oldest 100 (or so) records from the lifespanlist.

It is also true that not all IAM digits are of interest. In the case of800 numbers, the destination may change switches based on date and time.Thus the information cannot be kept in the ISUP Learning tree. The ISUPLearning Exception configurable objects can be used to define whichprefix digits are not to be learned. If the IAM's digits match any ofthe exception prefixes, the digits are not learned.

In the case of mated-pair configuration, the ISUP learning informationis gathered at the PCE 100 peers receiving the ISUP IAM messages. Asmost TCAP services are sent via connectionless messages such as UDTs,the Public TCAP query associated with a given digits may not be receivedat the same PCE 100 peer, which received the IAM. Thus, the ISUPlearning information must be available to all PCE peers for propermanagement.

The user can change the distribute implementation during run time,typically from Broadcast to Query-and-Response (ISUP Learning MaxDelay>0). During the transition between the two implementations, thepeers will simply return multiple successful responses until theirrecord lifespan expired.

On the rare event that a Query-and-Response is modified to a Broadcastimplementation, the Public TCAP query will not find the digits for oldISUP Learning records unless they are received on the proper peer. Anynew records will be properly processed, which should allow most “class5” features which send their IAM prior to their corresponding TCAP. TheISUP Learning information will be reset once the old records expire forat most ISUP Learning Lifespan seconds.

The ISUP Learning records are created or updated based on a receivedIAM. The new or updated record is then broadcast to all PCE peers fordistribution management. Even if the record is already present, theupdated record is broadcast to update the Private Node name if necessaryand to reset the record lifespan at each PCE peer. On receipt of aPublic TCAP message, the local ISUP Learning number tree is queried tosee if the digits are learned.

For race conditions, the broadcast record should arrive at the PCE 100peer prior to the Public TCAP query as the query if often sent followingIAM processing such as once the call is closed due to a busy signal. TheIAM processing at the remote end should ensure enough time for the ISUPLearning record to be distributed. If the TCAP is received prior to thebroadcast, the query will be simply treated as unlearned digits.

FIG. 6 is a call flow diagram illustrating ISUP learning feature of thepresent invention. Assuming that a subscriber on Public Node 131 place acall, causing Public Node 131 to generate and transmit IAM message 170.Through PCE 100, IAM message 171 is routed (while PCE 100 processes thenecessary steps and manipulations to route the message properly) toPrivate Node 231. Assume that there is no resource available to acceptthis call, thus Private Node 231 generates and transmit REL message 172back, through PCE 100, and the message 173 is reached to Public Node131. Then, the subscriber subsequently dial “*66”, which causes PublicNode 131 to generate and transmit TCAP Query Invoke message 178 boundedto PCE 100. Since PCE 100 has already handled and examined IAM message170 previously, thus PCE 100 determines to route TCAP Query Invokemessage 178 to Private Node 231 based on called party digits. PCE 100processes the message (and records TIDs in the hash tables 41 and 42)and transmit the message 177 to Private Node 231. Once Private Node 231receives the message 177, and after processes the query, Private Node231 generates and transmits TCAP Result message 179. PCE 100 interceptsthe message, looks up and retrieve from the hash tables 41 and 42 thecorresponding TID. PCE 100, then, converts TID and OPC, and forwards themessage 180 to Public Node 131.

IAM digit learning may be managed locally at the system 1. On receipt ofa Public TCAP query requiring ISUP Learning, a query is sent out to allpeers (regardless if the local peer has a known record) while keeping acopy of the SCCP encoded message. The peers respond with an error or asuccess with the private node name and expiry time. When all theresponses are received or the Max Delay timer expires, the most recententry is used. If there is no entry, the ISUP Learning fails andprocessing for the Public TCAP query continues with the Broadcast toPrivate option.

It is to be noted that each node in Private Network 20 is able tomaintain its own E164 number; however, the operator of Private Network20 wishes to hide such information from Public Network 10, sinceexposing private E164 number implies that a new network entry in PublicNetwork 10. For example, on outbound messages from Private Network 20 toPublic Network 10, the private E164 would have to be displayed to theoutside world as a public E164 number. On Inbound messages to PrivateNetwork 20, the appropriate E164 number shall be mapped to the messages.For solving such problem, Private Node record and Public Gateway recordhave a field for storing E164 numbers, thus PCE 100 is able to translateand route the messages to the appropriate node.

FIG. 7 illustrates a general process flow of PCE 100 handling a TCAPmessage originated from Public Network 10. Once PCE 100 intercepts theTCAP message originated from Public Network 10, PCE 100 checks in thedatabase 30, based on DPC of the message, whether GTT tunneling isprovisioned at step 300. If so, PCE 100 skips the steps and proceeds tostep 304; otherwise, PCE 100 proceeds to the step 301. Then, PCE 100further checks whether the provisional parameters for TCAP and PointCode mapping have been enabled at step 301; or else, the message isdiscarded at step 309′. The authorized user of PCE 100 may provisionthese parameters. If so, then, PCE 100 looks up the database 30 toconfirm whether it is for a New TCAP transaction at step 302. If so, OPCand Calling Party (CLG) information are converted at step 303, then, PCE100 further checks whether TID can be found via ISUP Learning orBroadcast is required to discover the corresponding information at step304. If so, PCE 100 retrieves information that are leaned through ISUPLearning or initiate broadcasting to Private Network 20 to discover theproper corresponding information at step 305; otherwise, the message isdiscarded at step 309. Returning to step 302, if the TCAP message wasnot for new transaction, then PCE 100 checks, if it is in a mated-peerconfiguration, whether TID may be found from the Peer PCE (not shown) atstep 306; otherwise, the message is discarded at step 309′. If so, PCE100 further looks up TID records in the database 30 or the hash tables41 and 42 to see if TID record exists at step 307. If TID is found, TID,DPC, OPC and CLG are converted and forward the message at step 308.Otherwise, the TCAP message will be discarded at step 309′.

FIG. 8 illustrates a general process flow of PCE 100 handling a TCAPmessage originated from Private network 20. Once PCE 100 receives a TCAPmessage originated from Private Network 20, PCE 100 looks up thestructured data storages 30, 41 and 42 to see if DPC match exists atstep 400. If so, PCE 100 further checks whether OPC mapping is beingprovisioned by the authorized user. If so, PCE 100 converts DPC, OPC,Called Party Number (CLD) and CLG at step 411; otherwise, the message isdiscarded at step 410. Going back to step 400, if DPC match was notfound, PCE 100 further checks in the database 30 GTT tunneling wasprovisioned based on DPC of the message at step 402. If so, PCE 100skips all the steps and proceeds to step 412 for direct transfer of themessage to Public Network 10; otherwise, PCE 100 proceeds and checkswhether the authorized user has provisioned TCAP & Point Code mappingfeature at step 403. If so, PCE 100 checks whether the message is for anew TCAP transaction and it is not unidirectional at step 404. If thatis false, PCE 100 skips and go directly to step 407, which will bediscussed in following; however, if it is true, then PCE 100 furtherexamines whether the message is for transaction initial message at step405. If so, PCE 100 creates a transaction record at step 406; otherwise,PCE 100 look up and see whether there is any transaction record at step409. If not true, then the message is discarded; otherwise, PCE 100skips the step 406 and proceeds to step 407. Once the transaction recordis created or retrieved, PCE 100 converts TID of TCAP message at step407. Then, at step 408, PCE 100 further converts DPC, CLG and CLD atstep 408.

It is to be understood that the embodiments and variations shown anddescribed herein are merely illustrations of the principles of thisinvention and that various modifications may be implemented by thoseskilled in the art without departing from the spirit and scope of theinvention. It is also to be understood that present invention may take aform of a computer program product on a computer-readable storage mediumhaving computer-readable and executable codes within the storage medium.

1. A Signaling System No. 7 (SS7) node for routing a transactioncapabilities application part (TCAP) message from a first node in afirst subnet to a second node in a second subnet in a SS7 network withsaid first and second nodes having the same point code, said nodecomprising: a) a first interface for said first subnet; b) a secondinterface for said second subnet; c) a processor in communication withsaid first and second interfaces, and further in communication with astructured database, wherein said processor carries out the processcomprising the steps of: i) preparing a first record for said first nodeand a second record for said second node in said structured database;ii) receiving said TCAP message from said first node through said firstinterface; iii) extracting originating point code (OPC), destinationpoint code (DPC) and transaction identifier (TID) of said TCAP message;iv) looking up and retrieving, from said structured database, saidsecond record for a corresponding OPC, a corresponding DPC and acorresponding TID partially or combinedly based on said OPC, said DPCand said TID of said received TCAP message; and v) replacing said OPC,said DPC and said TID of said received TCAP message with saidcorresponding OPC, said corresponding DPC, and said corresponding TID;and vi) forwarding said TCAP message with said corresponding OPC, saidcorresponding DPC, and said corresponding TID through said secondinterface.
 2. The SS7 node as recited in claim 1, wherein said firstsubnet is a public or private network.
 3. The SS7 node as recited inclaim 1, wherein said second subnet is a public or private network.
 4. Amethod of routing a transaction capabilities application part (TCAP)message from a first node in a first subnet to a second node in a secondsubnet in a SS7 network with said first and second nodes having the samepoint code, comprising the steps of: a) preparing a first record forsaid first node and a second record for said second node in a structureddatabase; b) at a node, receiving said TCAP message from said first nodein said first subnet through a first interface; c) at the node,extracting originating point code (OPC), destination point code (DPC)and transaction identifier (TID) of said TCAP message; d) looking up andretrieving, from said structured database, said second record for acorresponding OPC, a corresponding DPC and a corresponding TID partiallyor combinedly based on said OPC, said DPC and said TID of said receivedTCAP message; e) replacing said OPC, said DPC and said TID of saidreceived TCAP message with said corresponding OPC, said correspondingDPC, and said corresponding TID; and f) from the node, forwarding saidTCAP message with said corresponding OPC, said corresponding DPC, andsaid corresponding TID to said second node in said second subnet througha second interface.
 5. The method as recited in claim 4, wherein saidfirst subnet is a public or private network.
 6. The method as recited inclaim 4, wherein said second subnet is a public or private network.
 7. Anon-transitory computer readable storage medium storing executablecomputer program instructions which, when executed at a node, causes thenode to perform a process of routing a transaction capabilitiesapplication part (TCAP) message from a first node in a first subnet to asecond node in a second subnet, with said first and second nodes havingthe same point code, comprising the steps of a) preparing a first recordfor said first node and a second record for said second node in astructured database; b) at the node, receiving said TCAP message fromsaid first node in said first subnet through a first interface; c) atthe node, extracting originating point code (OPC), destination pointcode (DPC) and transaction identifier (TID) of said TCAP message; d)looking up and retrieving, from said structured database, said secondrecord for a corresponding OPC, a corresponding DPC and a correspondingTID partially or combinedly based on said OPC, said DPC and said TID ofsaid received TCAP message; e) replacing said OPC, said DPC and said TIDof said received TCAP message with said corresponding OPC, saidcorresponding DPC, and said corresponding TID; and f) from the node,forwarding said TCAP message with said corresponding OPC, saidcorresponding DPC, and said corresponding TID to said second node insaid second subnet through a second interface.
 8. The computer readablestorage medium as recited in claim 7, wherein said first subnet is apublic or private network.
 9. The computer readable storage medium asrecited in claim 7, wherein said second subnet is a public or privatenetwork.